

<!DOCTYPE html>
<html class="writer-html5" lang="en" >
<head>
  <meta charset="utf-8" />
  
  <meta name="viewport" content="width=device-width, initial-scale=1.0" />
  
  <title>Running Integration Tests using Teuthology &mdash; Ceph Documentation</title>
  

  
  <link rel="stylesheet" href="../../../_static/ceph.css" type="text/css" />
  <link rel="stylesheet" href="../../../_static/pygments.css" type="text/css" />
  <link rel="stylesheet" href="../../../_static/graphviz.css" type="text/css" />
  <link rel="stylesheet" href="../../../_static/css/custom.css" type="text/css" />

  
  
    <link rel="shortcut icon" href="../../../_static/favicon.ico"/>
  

  
  

  

  
  <!--[if lt IE 9]>
    <script src="../../../_static/js/html5shiv.min.js"></script>
  <![endif]-->
  
    
      <script type="text/javascript" id="documentation_options" data-url_root="../../../" src="../../../_static/documentation_options.js"></script>
        <script src="../../../_static/jquery.js"></script>
        <script src="../../../_static/underscore.js"></script>
        <script src="../../../_static/doctools.js"></script>
    
    <script type="text/javascript" src="../../../_static/js/theme.js"></script>

    
    <link rel="index" title="Index" href="../../../genindex/" />
    <link rel="search" title="Search" href="../../../search/" /> 
</head>

<body class="wy-body-for-nav">

   
  <header class="top-bar">
    

















<div role="navigation" aria-label="breadcrumbs navigation">

  <ul class="wy-breadcrumbs">
    
      <li><a href="../../../" class="icon icon-home"></a> &raquo;</li>
        
      <li>Running Integration Tests using Teuthology</li>
    
    
      <li class="wy-breadcrumbs-aside">
        
          
            <a href="../../../_sources/dev/developer_guide/running-tests-using-teuth.rst.txt" rel="nofollow"> View page source</a>
          
        
      </li>
    
  </ul>

  
  <hr/>
</div>
  </header>
  <div class="wy-grid-for-nav">
    
    <nav data-toggle="wy-nav-shift" class="wy-nav-side">
      <div class="wy-side-scroll">
        <div class="wy-side-nav-search"  style="background: #eee" >
          

          
            <a href="../../../">
          

          
            
            <img src="../../../_static/logo.png" class="logo" alt="Logo"/>
          
          </a>

          

          
<div role="search">
  <form id="rtd-search-form" class="wy-form" action="../../../search/" method="get">
    <input type="text" name="q" placeholder="Search docs" />
    <input type="hidden" name="check_keywords" value="yes" />
    <input type="hidden" name="area" value="default" />
  </form>
</div>

          
        </div>

        
        <div class="wy-menu wy-menu-vertical" data-spy="affix" role="navigation" aria-label="main navigation">
          
            
            
              
            
            
              <ul>
<li class="toctree-l1"><a class="reference internal" href="../../../start/intro/">Ceph 简介</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../install/">安装 Ceph</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../cephadm/">Cephadm</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../rados/">Ceph 存储集群</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../cephfs/">Ceph 文件系统</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../rbd/">Ceph 块设备</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../radosgw/">Ceph 对象网关</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../mgr/">Ceph 管理器守护进程</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../mgr/dashboard/">Ceph 仪表盘</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../api/">API 文档</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../architecture/">体系结构</a></li>
<li class="toctree-l1"><a class="reference internal" href="../">开发者指南</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../internals/">Ceph 内幕</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../governance/">项目管理</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../foundation/">Ceph 基金会</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../ceph-volume/">ceph-volume</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../releases/general/">Ceph 版本（总目录）</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../releases/">Ceph 版本（索引）</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../security/">Security</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../glossary/">Ceph 术语</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../jaegertracing/">Tracing</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../../translation_cn/">中文版翻译资源</a></li>
</ul>

            
          
        </div>
        
      </div>
    </nav>

    <section data-toggle="wy-nav-shift" class="wy-nav-content-wrap">

      
      <nav class="wy-nav-top" aria-label="top navigation">
        
          <i data-toggle="wy-nav-top" class="fa fa-bars"></i>
          <a href="../../../">Ceph</a>
        
      </nav>


      <div class="wy-nav-content">
        
        <div class="rst-content">
        
          <div role="main" class="document" itemscope="itemscope" itemtype="http://schema.org/Article">
           <div itemprop="articleBody">
            
<div id="dev-warning" class="admonition note">
  <p class="first admonition-title">Notice</p>
  <p class="last">This document is for a development version of Ceph.</p>
</div>
  <div id="docubetter" align="right" style="padding: 5px; font-weight: bold;">
    <a href="https://pad.ceph.com/p/Report_Documentation_Bugs">Report a Documentation Bug</a>
  </div>

  
  <div class="section" id="running-integration-tests-using-teuthology">
<h1>Running Integration Tests using Teuthology<a class="headerlink" href="#running-integration-tests-using-teuthology" title="Permalink to this headline">¶</a></h1>
<div class="section" id="getting-binaries">
<h2>Getting binaries<a class="headerlink" href="#getting-binaries" title="Permalink to this headline">¶</a></h2>
<p>To run integration tests using teuthology, you need to have Ceph binaries
built for your branch. Follow these steps to initiate the build process -</p>
<ol class="arabic simple">
<li><p>Push the branch to <a class="reference external" href="https://github.com/ceph/ceph-ci">ceph-ci</a> repository. This triggers the process of
building the binaries.</p></li>
<li><p>To confirm that the build process has been initiated, spot the branch name
at <a class="reference external" href="https://shaman.ceph.com/builds/ceph/">Shaman</a>. Little after the build process has been initiated, the single
entry with your branch name would multiply, each new entry for a different
combination of distro and flavour.</p></li>
<li><p>Wait until the packages are built and uploaded, and the repository offering
them are created. This is marked by colouring the entries for the branch
name green. Preferably, wait until each entry is coloured green. Usually,
it takes around 2-3 hours depending on the availability of the machines.</p></li>
</ol>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>Branch to be pushed on ceph-ci can be any branch, it shouldn’t
necessarily be a PR branch.</p>
</div>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>In case you are pushing master or any other standard branch, check
<a class="reference external" href="https://shaman.ceph.com/builds/ceph/">Shaman</a> beforehand since it already might have builds ready for it.</p>
</div>
</div>
<div class="section" id="triggering-tests">
<h2>Triggering Tests<a class="headerlink" href="#triggering-tests" title="Permalink to this headline">¶</a></h2>
<p>After building is complete, proceed to trigger tests -</p>
<ol class="arabic">
<li><p>Log in to the teuthology machine:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">ssh</span> <span class="o">&lt;</span><span class="n">username</span><span class="o">&gt;</span><span class="nd">@teuthology</span><span class="o">.</span><span class="n">front</span><span class="o">.</span><span class="n">sepia</span><span class="o">.</span><span class="n">ceph</span><span class="o">.</span><span class="n">com</span>
</pre></div>
</div>
<p>This would require Sepia lab access. To know how to request it, see: <a class="reference external" href="https://ceph.github.io/sepia/adding_users/">https://ceph.github.io/sepia/adding_users/</a></p>
</li>
<li><p>Next, get teuthology installed. Run the first set of commands in
<a class="reference external" href="../running-tests-locally/#running-your-first-test">Running Your First Test</a> for that. After that, activate the virtual
environment in which teuthology is installed.</p></li>
<li><p>Run the <code class="docutils literal notranslate"><span class="pre">teuthology-suite</span></code> command:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">teuthology</span><span class="o">-</span><span class="n">suite</span> <span class="o">-</span><span class="n">v</span> <span class="o">-</span><span class="n">m</span> <span class="n">smithi</span> <span class="o">-</span><span class="n">c</span> <span class="n">wip</span><span class="o">-</span><span class="n">devname</span><span class="o">-</span><span class="n">feature</span><span class="o">-</span><span class="n">x</span> <span class="o">-</span><span class="n">s</span> <span class="n">fs</span> <span class="o">-</span><span class="n">p</span> <span class="mi">110</span> <span class="o">--</span><span class="nb">filter</span> <span class="s2">&quot;cephfs-shell&quot;</span>
</pre></div>
</div>
<dl>
<dt>Following are the options used in above command with their meanings -</dt><dd><dl class="option-list">
<dt><kbd><span class="option">-v</span></kbd></dt>
<dd><p>verbose</p>
</dd>
<dt><kbd><span class="option">-m</span></kbd></dt>
<dd><p>machine name</p>
</dd>
<dt><kbd><span class="option">-c</span></kbd></dt>
<dd><p>branch name, the branch that was pushed on ceph-ci</p>
</dd>
<dt><kbd><span class="option">-s</span></kbd></dt>
<dd><p>test-suite name</p>
</dd>
<dt><kbd><span class="option">-p</span></kbd></dt>
<dd><p>higher the number, lower the priority of the job</p>
</dd>
<dt><kbd><span class="option">--filter</span></kbd></dt>
<dd><p>filter tests in given suite that needs to run, the arg to
filter should be the test you want to run</p>
</dd>
</dl>
</dd>
</dl>
</li>
</ol>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>The priority number present in the command above is just a
placeholder. It might be highly inappropriate for the jobs you may want to
trigger. See <a class="reference external" href="../tests-integration-tests/#testing-priority">Testing Priority</a> section to pick a priority number.</p>
</div>
<div class="admonition note">
<p class="admonition-title">Note</p>
<p>Don’t skip passing a priority number, the default value is 1000
which way too high; the job probably might never run.</p>
</div>
<ol class="arabic simple">
<li><p>Wait for the tests to run. <code class="docutils literal notranslate"><span class="pre">teuthology-suite</span></code> prints a link to the
<a class="reference external" href="http://pulpito.front.sepia.ceph.com/">Pulpito</a> page created for the tests triggered.</p></li>
</ol>
<p>Other frequently used/useful options are <code class="docutils literal notranslate"><span class="pre">-d</span></code> (or <code class="docutils literal notranslate"><span class="pre">--distro</span></code>),
<code class="docutils literal notranslate"><span class="pre">--distroversion</span></code>, <code class="docutils literal notranslate"><span class="pre">--filter-out</span></code>, <code class="docutils literal notranslate"><span class="pre">--timeout</span></code>, <code class="docutils literal notranslate"><span class="pre">flavor</span></code>, <code class="docutils literal notranslate"><span class="pre">-rerun</span></code>,
<code class="docutils literal notranslate"><span class="pre">-l</span></code> (for limiting number of jobs) , <code class="docutils literal notranslate"><span class="pre">-n</span></code> (for how many times job would
run) and <code class="docutils literal notranslate"><span class="pre">-e</span></code> (for email notifications). Run <code class="docutils literal notranslate"><span class="pre">teuthology-suite</span> <span class="pre">--help</span></code>
to read description of these and every other options available.</p>
</div>
<div class="section" id="testing-qa-changes-without-re-building-binaires">
<h2>Testing QA changes (without re-building binaires)<a class="headerlink" href="#testing-qa-changes-without-re-building-binaires" title="Permalink to this headline">¶</a></h2>
<p>While writing a PR you might need to test your PR repeatedly using teuthology.
If you are making non-QA changes, you need to follow the standard process of
triggering builds, waiting for it to finish and then triggering tests and
wait for the result. But if changes you made are purely changes in qa/,
you don’t need rebuild the binaries. Instead you can test binaries built for
the ceph-ci branch and instruct <code class="docutils literal notranslate"><span class="pre">teuthology-suite</span></code> command to use a separate
branch for running tests. The separate branch can be passed to the command
by using <code class="docutils literal notranslate"><span class="pre">--suite-repo</span></code> and <code class="docutils literal notranslate"><span class="pre">--suite-branch</span></code>. Pass the link to the GitHub
fork where your PR branch exists to the first option and pass the PR branch
name to the second option.</p>
<p>For example, if you want to make changes in <code class="docutils literal notranslate"><span class="pre">qa/</span></code> after testing <code class="docutils literal notranslate"><span class="pre">branch-x</span></code>
(of which has ceph-ci branch is <code class="docutils literal notranslate"><span class="pre">wip-username-branch-x</span></code>) by running
following command:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">teuthology</span><span class="o">-</span><span class="n">suite</span> <span class="o">-</span><span class="n">v</span> <span class="o">-</span><span class="n">m</span> <span class="n">smithi</span> <span class="o">-</span><span class="n">c</span> <span class="n">wip</span><span class="o">-</span><span class="n">username</span><span class="o">-</span><span class="n">branch</span><span class="o">-</span><span class="n">x</span> <span class="o">-</span><span class="n">s</span> <span class="n">fs</span> <span class="o">-</span><span class="n">p</span> <span class="mi">50</span> <span class="o">--</span><span class="nb">filter</span> <span class="n">cephfs</span><span class="o">-</span><span class="n">shell</span>
</pre></div>
</div>
<p>You can make the modifications locally, update the PR branch and then
trigger tests from your PR branch as follows:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">teuthology</span><span class="o">-</span><span class="n">suite</span> <span class="o">-</span><span class="n">v</span> <span class="o">-</span><span class="n">m</span> <span class="n">smithi</span> <span class="o">-</span><span class="n">c</span> <span class="n">wip</span><span class="o">-</span><span class="n">username</span><span class="o">-</span><span class="n">branch</span><span class="o">-</span><span class="n">x</span> <span class="o">-</span><span class="n">s</span> <span class="n">fs</span> <span class="o">-</span><span class="n">p</span> <span class="mi">50</span> <span class="o">--</span><span class="nb">filter</span> <span class="n">cephfs</span><span class="o">-</span><span class="n">shell</span> <span class="o">--</span><span class="n">suite</span><span class="o">-</span><span class="n">repo</span> <span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">github</span><span class="o">.</span><span class="n">com</span><span class="o">/</span><span class="n">username</span><span class="o">/</span><span class="n">ceph</span> <span class="o">--</span><span class="n">suite</span><span class="o">-</span><span class="n">branch</span> <span class="n">branch</span><span class="o">-</span><span class="n">x</span>
</pre></div>
</div>
<p>You can verify if the tests were run using this branch by looking at values
for the keys <code class="docutils literal notranslate"><span class="pre">suite_branch</span></code>, <code class="docutils literal notranslate"><span class="pre">suite_repo</span></code> and <code class="docutils literal notranslate"><span class="pre">suite_sha1</span></code> in the job
config printed at the very beginning of the teuthology job.</p>
</div>
<div class="section" id="about-suites-and-filters">
<h2>About Suites and Filters<a class="headerlink" href="#about-suites-and-filters" title="Permalink to this headline">¶</a></h2>
<p>See <a class="reference external" href="../tests-integration-tests/#suites-inventory">Suites Inventory</a> for a list of suites of integration tests present
right now. Alternatively, each directory under <code class="docutils literal notranslate"><span class="pre">qa/suites</span></code> in Ceph
repository is an integration test suite, so looking within that directory
to decide an appropriate argument for <code class="docutils literal notranslate"><span class="pre">-s</span></code> also works.</p>
<p>For picking an argument for <code class="docutils literal notranslate"><span class="pre">--filter</span></code>, look within
<code class="docutils literal notranslate"><span class="pre">qa/suites/&lt;suite-name&gt;/&lt;subsuite-name&gt;/tasks</span></code> to get keywords for filtering
tests. Each YAML file in there can trigger a bunch of tests; using the name of
the file, without the extension part of the file name, as an argument to the
<code class="docutils literal notranslate"><span class="pre">--filter</span></code> will trigger those tests. For example, the sample command above
uses <code class="docutils literal notranslate"><span class="pre">cephfs-shell</span></code> since there’s a file named <code class="docutils literal notranslate"><span class="pre">cephfs-shell.yaml</span></code> in
<code class="docutils literal notranslate"><span class="pre">qa/suites/fs/basic_functional/tasks/</span></code>. In case, the file name doesn’t hint
what bunch of tests it would trigger, look at the contents of the file for
<code class="docutils literal notranslate"><span class="pre">modules</span></code> attribute. For <code class="docutils literal notranslate"><span class="pre">cephfs-shell.yaml</span></code> the <code class="docutils literal notranslate"><span class="pre">modules</span></code> attribute
is <code class="docutils literal notranslate"><span class="pre">tasks.cephfs.test_cephfs_shell</span></code> which means it’ll trigger all tests in
<code class="docutils literal notranslate"><span class="pre">qa/tasks/cephfs/test_cephfs_shell.py</span></code>.</p>
</div>
<div class="section" id="killing-tests">
<h2>Killing Tests<a class="headerlink" href="#killing-tests" title="Permalink to this headline">¶</a></h2>
<p>Sometimes a teuthology job might not complete running for several minutes or
even hours after tests that were trigged have completed running and other
times wrong set of tests can be triggered is filter wasn’t chosen carefully.
To save resource it’s better to termniate such a job. Following is the command
to terminate a job:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">teuthology</span><span class="o">-</span><span class="n">kill</span> <span class="o">-</span><span class="n">r</span> <span class="n">teuthology</span><span class="o">-</span><span class="mi">2019</span><span class="o">-</span><span class="mi">12</span><span class="o">-</span><span class="mi">10_05</span><span class="p">:</span><span class="mi">00</span><span class="p">:</span><span class="mi">03</span><span class="o">-</span><span class="n">smoke</span><span class="o">-</span><span class="n">master</span><span class="o">-</span><span class="n">testing</span><span class="o">-</span><span class="n">basic</span><span class="o">-</span><span class="n">smithi</span>
</pre></div>
</div>
<p>Let’s call the the argument passed to <code class="docutils literal notranslate"><span class="pre">-r</span></code> as test ID. It can be found
easily in the link to the Pulpito page for the tests you triggered. For
example, for the above test ID, the link is - <a class="reference external" href="http://pulpito.front.sepia.ceph.com/teuthology-2019-12-10_05:00:03-smoke-master-testing-basic-smithi/">http://pulpito.front.sepia.ceph.com/teuthology-2019-12-10_05:00:03-smoke-master-testing-basic-smithi/</a></p>
</div>
<div class="section" id="re-running-tests">
<h2>Re-running Tests<a class="headerlink" href="#re-running-tests" title="Permalink to this headline">¶</a></h2>
<p>Pass <code class="docutils literal notranslate"><span class="pre">--rerun</span></code> option, with test ID as an argument to it, to
<code class="docutils literal notranslate"><span class="pre">teuthology-suite</span></code> command:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">teuthology</span><span class="o">-</span><span class="n">suite</span> <span class="o">-</span><span class="n">v</span> <span class="o">-</span><span class="n">m</span> <span class="n">smithi</span> <span class="o">-</span><span class="n">c</span> <span class="n">wip</span><span class="o">-</span><span class="n">rishabh</span><span class="o">-</span><span class="n">fs</span><span class="o">-</span><span class="n">test_cephfs_shell</span><span class="o">-</span><span class="n">fix</span> <span class="o">-</span><span class="n">p</span> <span class="mi">50</span> <span class="o">--</span><span class="n">rerun</span> <span class="n">teuthology</span><span class="o">-</span><span class="mi">2019</span><span class="o">-</span><span class="mi">12</span><span class="o">-</span><span class="mi">10_05</span><span class="p">:</span><span class="mi">00</span><span class="p">:</span><span class="mi">03</span><span class="o">-</span><span class="n">smoke</span><span class="o">-</span><span class="n">master</span><span class="o">-</span><span class="n">testing</span><span class="o">-</span><span class="n">basic</span><span class="o">-</span><span class="n">smithi</span>
</pre></div>
</div>
<p>The meaning of rest of the options is already covered in <cite>Triggering Tests</cite>
section.</p>
</div>
<div class="section" id="teuthology-archives">
<h2>Teuthology Archives<a class="headerlink" href="#teuthology-archives" title="Permalink to this headline">¶</a></h2>
<p>Once the tests have finished running, the log for the job can be obtained by
clicking on job ID at the Pulpito page for your tests. It’s more convenient to
download the log and then view it rather than viewing it in an internet
browser since these logs can easily be upto size of 1 GB. What’s much more
easier is to log in to the teuthology machine again
(<code class="docutils literal notranslate"><span class="pre">teuthology.front.sepia.ceph.com</span></code>), and access the following path:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="o">/</span><span class="n">ceph</span><span class="o">/</span><span class="n">teuthology</span><span class="o">-</span><span class="n">archive</span><span class="o">/&lt;</span><span class="n">test</span><span class="o">-</span><span class="nb">id</span><span class="o">&gt;/&lt;</span><span class="n">job</span><span class="o">-</span><span class="nb">id</span><span class="o">&gt;/</span><span class="n">teuthology</span><span class="o">.</span><span class="n">log</span>
</pre></div>
</div>
<p>For example, for above test ID path is:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="o">/</span><span class="n">ceph</span><span class="o">/</span><span class="n">teuthology</span><span class="o">-</span><span class="n">archive</span><span class="o">/</span><span class="n">teuthology</span><span class="o">-</span><span class="mi">2019</span><span class="o">-</span><span class="mi">12</span><span class="o">-</span><span class="mi">10_05</span><span class="p">:</span><span class="mi">00</span><span class="p">:</span><span class="mi">03</span><span class="o">-</span><span class="n">smoke</span><span class="o">-</span><span class="n">master</span><span class="o">-</span><span class="n">testing</span><span class="o">-</span><span class="n">basic</span><span class="o">-</span><span class="n">smithi</span><span class="o">/</span><span class="mi">4588482</span><span class="o">/</span><span class="n">teuthology</span><span class="o">.</span><span class="n">log</span>
</pre></div>
</div>
<p>This way the log remotely can be viewed remotely without having to wait too
much.</p>
</div>
<div class="section" id="naming-the-ceph-ci-branch">
<h2>Naming the ceph-ci branch<a class="headerlink" href="#naming-the-ceph-ci-branch" title="Permalink to this headline">¶</a></h2>
<p>There are no hard conventions (except for the case of stable branch; see
next paragraph) for how the branch pushed on ceph-ci is named. But, to make
builds and tests easily identitifiable on Shaman and Pulpito respectively,
prepend it with your name. For example branch <code class="docutils literal notranslate"><span class="pre">feature-x</span></code> can be named
<code class="docutils literal notranslate"><span class="pre">wip-yourname-feature-x</span></code> while pushing on ceph-ci.</p>
<p>In case you are using one of the stable branches (e.g.  nautilis, mimic,
etc.), include the name of that stable branch in your ceph-ci branch name.
For example, <code class="docutils literal notranslate"><span class="pre">feature-x</span></code> PR branch should be named as
<code class="docutils literal notranslate"><span class="pre">wip-feature-x-nautilus</span></code>. <em>This is not just a matter of convention but this,
more essentially, builds your branch in the correct environment.</em></p>
<p>Delete the branch from ceph-ci, once it’s not required anymore. If you are
logged in at GitHub, all your branches on ceph-ci can be easily found here -
<a class="reference external" href="https://github.com/ceph/ceph-ci/branches">https://github.com/ceph/ceph-ci/branches</a>.</p>
</div>
</div>



           </div>
           
          </div>
          <footer>

  <hr/>

  <div role="contentinfo">
    <p>
        &#169; Copyright 2016, Ceph authors and contributors. Licensed under Creative Commons Attribution Share Alike 3.0 (CC-BY-SA-3.0).

    </p>
  </div> 

</footer>
        </div>
      </div>

    </section>

  </div>
  

  <script type="text/javascript">
      jQuery(function () {
          SphinxRtdTheme.Navigation.enable(true);
      });
  </script>

  
  
    
   

</body>
</html>